User plane for fifth generation cellular architecture

ABSTRACT

Apparatuses, systems, and methods to perform attachment of a wireless device to a next generation gateway via either a base station of a next generation radio access network (RAN) or a mobility management entity of a legacy RAN. An apparatus may be configured to receive an attachment request from a wireless device, determine authentication information via communication with a home subscriber server, determine, based at least in part on the authentication information, whether the wireless device is capable of communicating via the next generation RAT, and send, in response to determining the wireless device is capable, a connection request to a gateway of the next generation RAN. The authentication information may include subscription information associated with the wireless device.

PRIORITY DATA

This application a continuation of, and claims benefit of priority to,U.S. patent application Ser. No. 15/030,159, titled “User Plane forFifth Generation Cellular Architecture”, filed Apr. 18, 2016, which isthe U.S. National Stage Application of International Patent ApplicationNo. PCT/CN2015/091174, titled “User Plane for Fifth Generation CellularArchitecture”, filed Sep. 30, 2015, each of which is hereby incorporatedby reference in its entirety as though fully and completely set forthherein.

The claims in the instant application are different than those of theparent application and/or other related applications. The Applicanttherefore rescinds any disclaimer of claim scope made in the parentapplication and/or any predecessor application in relation to theinstant application. Any such previous disclaimer and the citedreferences that it was made to avoid, may need to be revisited. Further,any disclaimer made in the instant application should not be read intoor against the parent application and/or other related applications.

FIELD

The present application relates to wireless devices, and moreparticularly to apparatus, systems, and methods for attaching a wirelessdevice to a gateway of a next generation radio access technology.

DESCRIPTION OF THE RELATED ART

Wireless communication systems are rapidly growing in usage. Further,wireless communication technology has evolved from voice-onlycommunications to also include the transmission of data, such asInternet and multimedia content. Thus, improvements in the field aredesired.

SUMMARY

Embodiments relate to apparatuses, systems, and methods to performattachment of a wireless device to a next generation gateway via eithera base station of a next generation radio access network (RAN) or amobility management entity of a legacy RAN. The apparatuses, systems,and methods presented herein may allow for internet protocol (IP)address continuity for a wireless device as the wireless devices movesbetween legacy RANs and the next generation RAN.

According to some embodiments, an apparatus may be configured to receivean attachment request from a wireless device, determine authenticationinformation via communication with a home subscriber server, determine,based at least in part on the authentication information, whether thewireless device is capable of communicating via the next generation RAT,and send, in response to determining the wireless device is capable, aconnection request to a gateway of the next generation RAN. Theauthentication information may include subscription informationassociated with the wireless device.

In some embodiments, a base station (e.g., a base station in the nextgeneration RAN) may include a radio and a processing element operativelycoupled to the radio. The base station may be configured to receive anattachment request from the wireless device and determine authenticationinformation via communication with a home subscriber server (HSS). Inaddition, the base station may be configured to determine, based atleast in part on the authentication information, whether the wirelessdevice is capable of communication via a next generation radio accessnetwork (RAN) and send, in response to determining that the wirelessdevice is capable of communication via the next generation RAN, aconnection request to a gateway of the next generation RAN.

In some embodiments, a network node may include a processing elementconfigured to receive, from a base station (e.g., a base station in alegacy RAN), an attachment request for a wireless device and send anauthentication request to a HSS. The processing element may also beconfigured to receive authentication information from the HSS anddetermine, based at least in part on the authentication information,whether the wireless device is capable of communication via a nextgeneration RAN. Additionally, in response to determining that thewireless device is capable of communication via the next generation RAN,the processing element may be configured to send a connection request toa gateway of the next generation RAN.

In some embodiments, a processing element of a network node may executeprogram instructions stored on a non-transitory computer accessiblememory medium which may cause the network node to receive, from a basestation (e.g., a base station in a legacy RAN), an attachment requestfor a wireless device and send an authentication request to a HSS.Further, program instructions, when executed, may cause the network nodeto receive authentication information from the HSS and determine, basedat least in part on the authentication information, whether the wirelessdevice is capable of communication via a next generation RAN.Additionally, when executed, the program instructions may cause thenetwork node to send, in response to determining that the wirelessdevice is capable of communication via the next generation RAN, amessage to the wireless device, wherein the message indicates that theattachment request has been denied. The message may include a requestfor the wireless device to attach via a next generation base station.

The techniques described herein may be implemented in and/or used with anumber of different types of devices, including but not limited tocellular phones, tablet computers, wearable computing devices, portablemedia players, and any of various other computing devices.

This Summary is intended to provide a brief overview of some of thesubject matter described in this document. Accordingly, it will beappreciated that the above-described features are merely examples andshould not be construed to narrow the scope or spirit of the subjectmatter described herein in any way. Other features, aspects, andadvantages of the subject matter described herein will become apparentfrom the following Detailed Description, Figures, and Claims.

BRIEF DESCRIPTION OF THE DRAWINGS

A better understanding of the present subject matter can be obtainedwhen the following detailed description of various embodiments isconsidered in conjunction with the following drawings, in which:

FIG. 1 illustrates an example wireless communication system according tosome embodiments;

FIG. 2 illustrates a base station (BS) in communication with a userequipment (UE) device according to some embodiments;

FIG. 3 illustrates an example block diagram of a UE according to someembodiments;

FIG. 4 illustrates an example block diagram of a BS according to someembodiments;

FIGS. 5A-5C illustrate possible implementations of a next generationRAT, according to the prior art;

FIG. 6A illustrates a next generation network interface architectureaccording to some embodiments;

FIG. 6B illustrates a next generation network interface architectureaccording to some embodiments;

FIGS. 7A and 7B illustrate signaling diagrams for IP address continuityaccording to some embodiments;

FIG. 8 illustrates a signaling diagram for IP address continuityaccording to some embodiments;

FIGS. 9A and 9B illustrate signaling diagrams for DNS queries accordingto some embodiments;

FIG. 10 illustrates a protocol stack for a next generation wirelesscommunication system according to some embodiments;

FIG. 11A illustrates an example of a method for a wireless device toattach to a next generation gateway, according to some embodiments; and

FIG. 11B illustrates a processing element including modules forattaching a wireless device to a next generation gateway, according tosome embodiments.

While the features described herein may be susceptible to variousmodifications and alternative forms, specific embodiments thereof areshown by way of example in the drawings and are herein described indetail. It should be understood, however, that the drawings and detaileddescription thereto are not intended to be limiting to the particularform disclosed, but on the contrary, the intention is to cover allmodifications, equivalents and alternatives falling within the spiritand scope of the subject matter as defined by the appended claims.

DETAILED DESCRIPTION

Terms

The following is a glossary of terms used in this disclosure:

Memory Medium—Any of various types of non-transitory memory devices orstorage devices. The term “memory medium” is intended to include aninstallation medium, e.g., a CD-ROM, floppy disks, or tape device; acomputer system memory or random access memory such as DRAM, DDR RAM,SRAM, EDO RAM, Rambus RAM, etc.; a non-volatile memory such as a Flash,magnetic media, e.g., a hard drive, or optical storage; registers, orother similar types of memory elements, etc. The memory medium mayinclude other types of non-transitory memory as well or combinationsthereof. In addition, the memory medium may be located in a firstcomputer system in which the programs are executed, or may be located ina second different computer system which connects to the first computersystem over a network, such as the Internet. In the latter instance, thesecond computer system may provide program instructions to the firstcomputer for execution. The term “memory medium” may include two or morememory mediums which may reside in different locations, e.g., indifferent computer systems that are connected over a network. The memorymedium may store program instructions (e.g., embodied as computerprograms) that may be executed by one or more processors.

Carrier Medium—a memory medium as described above, as well as a physicaltransmission medium, such as a bus, network, and/or other physicaltransmission medium that conveys signals such as electrical,electromagnetic, or digital signals.

Programmable Hardware Element—includes various hardware devicescomprising multiple programmable function blocks connected via aprogrammable interconnect. Examples include FPGAs (Field ProgrammableGate Arrays), PLDs (Programmable Logic Devices), FPOAs (FieldProgrammable Object Arrays), and CPLDs (Complex PLDs). The programmablefunction blocks may range from fine grained (combinatorial logic or lookup tables) to coarse grained (arithmetic logic units or processorcores). A programmable hardware element may also be referred to as“reconfigurable logic”.

Computer System—any of various types of computing or processing systems,including a personal computer system (PC), mainframe computer system,workstation, network appliance, Internet appliance, personal digitalassistant (PDA), television system, grid computing system, or otherdevice or combinations of devices. In general, the term “computersystem” can be broadly defined to encompass any device (or combinationof devices) having at least one processor that executes instructionsfrom a memory medium.

User Equipment (UE) (or “UE Device”)—any of various types of computersystems devices which are mobile or portable and which performs wirelesscommunications. Examples of UE devices include mobile telephones orsmart phones (e.g., iPhone™, Android™-based phones), portable gamingdevices (e.g., Nintendo DS™, PlayStation Portable™, Gameboy Advance™,iPhone™), laptops, wearable devices (e.g. smart watch, smart glasses),PDAs, portable Internet devices, music players, data storage devices, orother handheld devices, etc. In general, the term “UE” or “UE device”can be broadly defined to encompass any electronic, computing, and/ortelecommunications device (or combination of devices) which is easilytransported by a user and capable of wireless communication.

Base Station—The term “Base Station” has the full breadth of itsordinary meaning, and at least includes a wireless communication stationinstalled at a fixed location and used to communicate as part of awireless telephone system or radio system.

Processing Element—refers to various elements or combinations ofelements that are capable of performing a function in a device, such asa user equipment or a cellular network device. Processing elements mayinclude, for example: processors and associated memory, portions orcircuits of individual processor cores, entire processor cores,processor arrays, circuits such as an ASIC (Application SpecificIntegrated Circuit), programmable hardware elements such as a fieldprogrammable gate array (FPGA), as well any of various combinations ofthe above.

Channel—a medium used to convey information from a sender (transmitter)to a receiver. It should be noted that since characteristics of the term“channel” may differ according to different wireless protocols, the term“channel” as used herein may be considered as being used in a mannerthat is consistent with the standard of the type of device withreference to which the term is used. In some standards, channel widthsmay be variable (e.g., depending on device capability, band conditions,etc.). For example, LTE may support scalable channel bandwidths from 1.4MHz to 20 MHz. In contrast, WLAN channels may be 22 MHz wide whileBluetooth channels may be 1 Mhz wide. Other protocols and standards mayinclude different definitions of channels. Furthermore, some standardsmay define and use multiple types of channels, e.g., different channelsfor uplink or downlink and/or different channels for different uses suchas data, control information, etc.

Band—The term “band” has the full breadth of its ordinary meaning, andat least includes a section of spectrum (e.g., radio frequency spectrum)in which channels are used or set aside for the same purpose.

Automatically—refers to an action or operation performed by a computersystem (e.g., software executed by the computer system) or device (e.g.,circuitry, programmable hardware elements, ASICs, etc.), without userinput directly specifying or performing the action or operation. Thusthe term “automatically” is in contrast to an operation being manuallyperformed or specified by the user, where the user provides input todirectly perform the operation. An automatic procedure may be initiatedby input provided by the user, but the subsequent actions that areperformed “automatically” are not specified by the user, i.e., are notperformed “manually”, where the user specifies each action to perform.For example, a user filling out an electronic form by selecting eachfield and providing input specifying information (e.g., by typinginformation, selecting check boxes, radio selections, etc.) is fillingout the form manually, even though the computer system must update theform in response to the user actions. The form may be automaticallyfilled out by the computer system where the computer system (e.g.,software executing on the computer system) analyzes the fields of theform and fills in the form without any user input specifying the answersto the fields. As indicated above, the user may invoke the automaticfilling of the form, but is not involved in the actual filling of theform (e.g., the user is not manually specifying answers to fields butrather they are being automatically completed). The presentspecification provides various examples of operations beingautomatically performed in response to actions the user has taken.

Approximately—refers to a value that is almost correct or exact. Forexample, approximately may refer to a value that is within 1 to 10percent of the exact (or desired) value. It should be noted, however,that the actual threshold value (or tolerance) may be applicationdependent. For example, in some embodiments, “approximately” may meanwithin 0.1% of some specified or desired value, while in various otherembodiments, the threshold may be, for example, 2%, 3%, 5%, and soforth, as desired or as required by the particular application.

Various components may be described as “configured to” perform a task ortasks. In such contexts, “configured to” is a broad recitation generallymeaning “having structure that” performs the task or tasks duringoperation. As such, the component can be configured to perform the taskeven when the component is not currently performing that task (e.g., aset of electrical conductors may be configured to electrically connect amodule to another module, even when the two modules are not connected).In some contexts, “configured to” may be a broad recitation of structuregenerally meaning “having circuitry that” performs the task or tasksduring operation. As such, the component can be configured to performthe task even when the component is not currently on. In general, thecircuitry that forms the structure corresponding to “configured to” mayinclude hardware circuits.

Various components may be described as performing a task or tasks, forconvenience in the description. Such descriptions should be interpretedas including the phrase “configured to.” Reciting a component that isconfigured to perform one or more tasks is expressly intended not toinvoke 35 U.S.C. § 112(f) interpretation for that component.

FIGS. 1 and 2—Communication System

FIG. 1 illustrates a simplified example wireless communication system,according to some embodiments. It is noted that the system of FIG. 1 ismerely one example of a possible system, and that features of thisdisclosure may be implemented in any of various systems, as desired.

As shown, the example wireless communication system includes a basestation 102A which communicates over a transmission medium with one ormore user devices 106A, 106B, etc., through 106N. Each of the userdevices may be referred to herein as a “user equipment” (UE). Thus, theuser devices 106 are referred to as UEs or UE devices.

The base station (BS) 102A may be a base transceiver station (BTS) orcell site (a “cellular base station”), and may include hardware thatenables wireless communication with the UEs 106A through 106N.

The communication area (or coverage area) of the base station may bereferred to as a “cell.” The base station 102A and the UEs 106 may beconfigured to communicate over the transmission medium using any ofvarious radio access technologies (RATs), also referred to as wirelesscommunication technologies, or telecommunication standards, such as GSM,UMTS (associated with, for example, WCDMA or TD-SCDMA air interfaces),LTE, LTE-Advanced (LTE-A), HSPA, 3GPP2 CDMA2000 (e.g., 1×RTT, 1×EV-DO,HRPD, eHRPD), etc. Note that if the base station 102A is implemented inthe context of LTE, it may alternately be referred to as an ‘eNodeB’.

As shown, the base station 102A may also be equipped to communicate witha network 100 (e.g., a core network of a cellular service provider, atelecommunication network such as a public switched telephone network(PSTN), and/or the Internet, among various possibilities). Thus, thebase station 102A may facilitate communication between the user devicesand/or between the user devices and the network 100. In particular, thecellular base station 102A may provide UEs 106 with varioustelecommunication capabilities, such as voice, SMS and/or data services.

Base station 102A and other similar base stations (such as base stations102B . . . 102N) operating according to the same or a different cellularcommunication standard may thus be provided as a network of cells, whichmay provide continuous or nearly continuous overlapping service to UEs106A-N and similar devices over a wide geographic area via one or morecellular communication standards.

Thus, while base station 102A may act as a “serving cell” for UEs 106A-Nas illustrated in FIG. 1, each UE 106 may also be capable of receivingsignals from (and possibly within communication range of) one or moreother cells (which might be provided by base stations 102B-N and/or anyother base stations), which may be referred to as “neighboring cells”.Such cells may also be capable of facilitating communication betweenuser devices and/or between user devices and the network 100. Such cellsmay include “macro” cells, “micro” cells, “pico” cells, and/or cellswhich provide any of various other granularities of service area size.For example, base stations 102A-B illustrated in FIG. 1 might be macrocells, while base station 102N might be a micro cell. Otherconfigurations are also possible.

Note that a UE 106 may be capable of communicating using multiplewireless communication standards. For example, the UE 106 may beconfigured to communicate using a wireless networking (e.g., Wi-Fi)and/or peer-to-peer wireless communication protocol (e.g., Bluetooth,Wi-Fi peer-to-peer, etc.) in addition to at least one cellularcommunication protocol (e.g., GSM, UMTS (associated with, for example,WCDMA or TD-SCDMA air interfaces), LTE, LTE-A, HSPA, 3GPP2 CDMA2000(e.g., 1×RTT, 1×EV-DO, HRPD, eHRPD), etc.). The UE 106 may also oralternatively be configured to communicate using one or more globalnavigational satellite systems (GNSS, e.g., GPS or GLONASS), one or moremobile television broadcasting standards (e.g., ATSC-M/H or DVB-H),and/or any other wireless communication protocol, if desired. Othercombinations of wireless communication standards (including more thantwo wireless communication standards) are also possible.

FIG. 2 illustrates user equipment 106 (e.g., one of the devices 106Athrough 106N) in communication with a base station 102, according tosome embodiments. The UE 106 may be a device with cellular communicationcapability such as a mobile phone, a hand-held device, a computer or atablet, or virtually any type of wireless device.

The UE 106 may include a processor that is configured to execute programinstructions stored in memory. The UE 106 may perform any of the methodembodiments described herein by executing such stored instructions.Alternatively, or in addition, the UE 106 may include a programmablehardware element such as an FPGA (field-programmable gate array) that isconfigured to perform any of the method embodiments described herein, orany portion of any of the method embodiments described herein.

The UE 106 may include one or more antennas for communicating using oneor more wireless communication protocols or technologies. In someembodiments, the UE 106 may be configured to communicate using, forexample, CDMA2000 (1×RTT/1×EV-DO/HRPD/eHRPD) or LTE using a singleshared radio and/or GSM or LTE using the single shared radio. The sharedradio may couple to a single antenna, or may couple to multiple antennas(e.g., for MIMO) for performing wireless communications. In general, aradio may include any combination of a baseband processor, analog RFsignal processing circuitry (e.g., including filters, mixers,oscillators, amplifiers, etc.), or digital processing circuitry (e.g.,for digital modulation as well as other digital processing). Similarly,the radio may implement one or more receive and transmit chains usingthe aforementioned hardware. For example, the UE 106 may share one ormore parts of a receive and/or transmit chain between multiple wirelesscommunication technologies, such as those discussed above.

In some embodiments, the UE 106 may include separate transmit and/orreceive chains (e.g., including separate antennas and other radiocomponents) for each wireless communication protocol with which it isconfigured to communicate. As a further possibility, the UE 106 mayinclude one or more radios which are shared between multiple wirelesscommunication protocols, and one or more radios which are usedexclusively by a single wireless communication protocol. For example,the UE 106 might include a shared radio for communicating using eitherof LTE or 1×RTT (or LTE or GSM), and separate radios for communicatingusing each of Wi-Fi and Bluetooth. Other configurations are alsopossible.

FIG. 3—Block Diagram of a UE

FIG. 3 illustrates an example block diagram of a UE 106, according tosome embodiments. As shown, the UE 106 may include a system on chip(SOC) 300, which may include portions for various purposes. For example,as shown, the SOC 300 may include processor(s) 302 which may executeprogram instructions for the UE 106 and display circuitry 304 which mayperform graphics processing and provide display signals to the display360. The processor(s) 302 may also be coupled to memory management unit(MMU) 340, which may be configured to receive addresses from theprocessor(s) 302 and translate those addresses to locations in memory(e.g., memory 306, read only memory (ROM) 350, NAND flash memory 310)and/or to other circuits or devices, such as the display circuitry 304,wireless communication circuitry 330, connector I/F 320, and/or display360. The MMU 340 may be configured to perform memory protection and pagetable translation or set up. In some embodiments, the MMU 340 may beincluded as a portion of the processor(s) 302.

As shown, the SOC 300 may be coupled to various other circuits of the UE106. For example, the UE 106 may include various types of memory (e.g.,including NAND flash 310), a connector interface 320 (e.g., for couplingto a computer system, dock, charging station, etc.), the display 360,and wireless communication circuitry 330 (e.g., for LTE, LTE-A,CDMA2000, Bluetooth, Wi-Fi, GPS, etc.).

As shown, the UE device 106 may include at least one antenna (andpossibly multiple antennas, e.g., for MIMO and/or for implementingdifferent wireless communication technologies, among variouspossibilities) for performing wireless communication with base stations,access points, and/or other devices. For example, the UE device 106 mayuse antenna 335 to perform the wireless communication.

The UE 106 may also include and/or be configured for use with one ormore user interface elements. The user interface elements may includeany of various elements, such as display 360 (which may be a touchscreendisplay), a keyboard (which may be a discrete keyboard or may beimplemented as part of a touchscreen display), a mouse, a microphoneand/or speakers, one or more cameras, one or more buttons, and/or any ofvarious other elements capable of providing information to a user and/orreceiving or interpreting user input.

The processor 302 of the UE device 106 may be configured to implementpart or all of the methods described herein, e.g., by executing programinstructions stored on a memory medium (e.g., a non-transitorycomputer-readable memory medium). In other embodiments, processor 302may be configured as a programmable hardware element, such as an FPGA(Field Programmable Gate Array), or as an ASIC (Application SpecificIntegrated Circuit). Alternatively (or in addition) the processor 302 ofthe UE 106, in conjunction with one or more of the other components 300,304, 306, 310, 320, 330, 340, 350, 360 may be configured to implementpart or all of the features described herein.

In addition, as described herein, processor 302 may be comprised of oneor more processing elements. In other words, one or more processingelements may be included in processor 302. Thus, processor 302 mayinclude one or more integrated circuits (ICs) that are configured toperform the functions of processor 302. In addition, each integratedcircuit may include circuitry (e.g., first circuitry, second circuitry,etc.) configured to perform the functions of processor 302.

Further, as described herein, radio 330 may be comprised of one or moreprocessing elements. In other words, one or more processing elements maybe included in radio 330. Thus, radio 330 may include one or moreintegrated circuits (ICs) that are configured to perform the functionsof radio 330. In addition, each integrated circuit may include circuitry(e.g., first circuitry, second circuitry, etc.) configured to performthe functions of radio 330.

FIG. 4—Block Diagram of a Base Station

FIG. 4 illustrates an example block diagram of a base station 102,according to some embodiments. It is noted that the base station of FIG.4 is merely one example of a possible base station. As shown, the basestation 102 may include processor(s) 404 which may execute programinstructions for the base station 102. The processor(s) 404 may also becoupled to memory management unit (MMU) 440, which may be configured toreceive addresses from the processor(s) 404 and translate thoseaddresses to locations in memory (e.g., memory 460 and read only memory(ROM) 450) or to other circuits or devices.

The base station 102 may include at least one network port 470. Thenetwork port 470 may be configured to couple to a telephone network andprovide a plurality of devices, such as UE devices 106, access to thetelephone network as described above in FIGS. 1 and 2.

The network port 470 (or an additional network port) may also oralternatively be configured to couple to a cellular network, e.g., acore network of a cellular service provider. The core network mayprovide mobility related services and/or other services to a pluralityof devices, such as UE devices 106. In some cases, the network port 470may couple to a telephone network via the core network, and/or the corenetwork may provide a telephone network (e.g., among other UE devicesserviced by the cellular service provider).

The base station 102 may include at least one antenna 434, and possiblymultiple antennas. The at least one antenna 434 may be configured tooperate as a wireless transceiver and may be further configured tocommunicate with UE devices 106 via radio 430. The antenna 434communicates with the radio 430 via communication chain 432.Communication chain 432 may be a receive chain, a transmit chain orboth. The radio 430 may be configured to communicate via variouswireless communication standards, including, but not limited to, LTE,LTE-A, GSM, UMTS, CDMA2000, Wi-Fi, etc.

The base station 102 may be configured to communicate wirelessly usingmultiple wireless communication standards. In some instances, the basestation 102 may include multiple radios, which may enable the basestation 102 to communicate according to multiple wireless communicationtechnologies. For example, as one possibility, the base station 102 mayinclude an LTE radio for performing communication according to LTE aswell as a Wi-Fi radio for performing communication according to Wi-Fi.In such a case, the base station 102 may be capable of operating as bothan LTE base station and a Wi-Fi access point. As another possibility,the base station 102 may include a multi-mode radio which is capable ofperforming communications according to any of multiple wirelesscommunication technologies (e.g., LTE and Wi-Fi, LTE and UMTS, LTE andCDMA2000, UMTS and GSM, etc.).

As described further subsequently herein, the BS 102 may includehardware and software components for implementing or supportingimplementation of features described herein. The processor 404 of thebase station 102 may be configured to implement or supportimplementation of part or all of the methods described herein, e.g., byexecuting program instructions stored on a memory medium (e.g., anon-transitory computer-readable memory medium). Alternatively, theprocessor 404 may be configured as a programmable hardware element, suchas an FPGA (Field Programmable Gate Array), or as an ASIC (ApplicationSpecific Integrated Circuit), or a combination thereof. Alternatively(or in addition) the processor 404 of the BS 102, in conjunction withone or more of the other components 430, 432, 434, 440, 450, 460, 470may be configured to implement or support implementation of part or allof the features described herein.

In addition, as described herein, processor(s) 404 may be comprised ofone or more processing elements. In other words, one or more processingelements may be included in processor(s) 404. Thus, processor(s) 404 mayinclude one or more integrated circuits (ICs) that are configured toperform the functions of processor(s) 404. In addition, each integratedcircuit may include circuitry (e.g., first circuitry, second circuitry,etc.) configured to perform the functions of processor(s) 404.

Further, as described herein, radio 430 may be comprised of one or moreprocessing elements. In other words, one or more processing elements maybe included in radio 430. Thus, radio 430 may include one or moreintegrated circuits (ICs) that are configured to perform the functionsof radio 430. In addition, each integrated circuit may include circuitry(e.g., first circuitry, second circuitry, etc.) configured to performthe functions of radio 430.

User Plane for Next Generation Cellular Network

FIGS. 5A-5C illustrate possible implementations of a next generationcellular network, according to the prior art. In general, eachimplementation is based on architecture design principles for radio,network, and operations and management of the next generation cellularnetwork (i.e., next generation RAN). For example, according to thearchitecture design principles, radios may leverage the radio frequency(RF) spectrum by exploiting higher frequencies and/or the unlicensed RFspectrum, split user and control planes, split uplink and downlink,and/or allow for multiple connectivity. As another example, radios mayenable cost-effective dense deployments via integration of third-partyand/or user deployments, automation of configuration, optimization, andhealing, enhancement of multi-RAT coordination, and/or support ofmulti-operator and/or shared use infrastructures. Further, radios maycoordinate and cancel interference by supporting expanded MIMO andcoordinated multipoint (CoMP) and exploiting controlled non-orthogonalinterference. In addition, radios may support dynamic radio topologiessuch as moving cells, relays, hubs, cloud radio access network (C-RAN)and distributed RAN (D-RAN) and support device to device communications(D2D) (e.g., for latency and/or disaster relief).

Additionally, according to the architecture design principles, nextgeneration networks may create a common composable core by minimizingentities and functionalities within the next generation network,splitting control and user planes, supporting a lean protocol stack, notrequiring any mandatory user plane functions, minimizing legacyinterworking, having a RAT-agnostic core, and supporting a convergenceof fixed (e.g., wired) and mobile (e.g., wireless) systems. Further,according to the architecture design principles, operations andmanagement may be simplified via automation and self-healing, probelessmonitoring, collaborative management, integrated OAM functionality, andcarrier-grade network cloud orchestration.

In addition to the principles directed to radios, networks, and OAM,next generation architecture design principles also include embracingflexible functions and capabilities such as network slicing, functionvariance, flexible function/service/application allocation, leveragingof network functions virtualization (NFV) and software definednetworking (SDN), state-disintegrated functions, and gracefuldegradation. Further, new value creation such as exploitation of bigdata and context awareness, exposing of radio and network APIs, andfacilitation of anything as a service (XaaS) should be supported.Additionally, security and privacy should be built in via extendingcontrol plane security (e.g., via HetNets) and ensuring location privacyand identity protection from (unlawful) disclosure.

Turning now to FIGS. 5A-5C, illustrated are possible implementations ofa next generation wireless communication architecture based on theprinciples described above, according to the prior art. As shown, FIG.5A illustrates an implementation in which there are defined interfacesbetween evolved packet core (EPC) 510 and existing 4G RAT 530 and nextgeneration (NG) RAT 540. Additionally, there is a defined interfacebetween fixed network (NW) 520 and fixed networks/Wi-Fi networks 550.Further, there is a potential interface between EPC 510 and fixed NW520. Main features of this architectural proposal include: (1) nochanges to the fourth generation (4G) RAN; and (2) such an architecturewould not require revolutionary next generation network function design.However, such an architecture would depend on the current legacyparadigm for all use cases, which may result in increased expenserelative to other approaches.

FIG. 5B illustrates another implementation based on the principlesdescribed above. As shown, such an implementation would introduce nextgeneration (NG) NW 515 which would include next generation networkfunctions. Thus, there would be defined interfaces between EPC 510 and4G RAT 530, NG NW 515 and NG RAT 540, fixed NW 520 and fixednetworks/Wi-Fi networks 550, and EPC 510 and NG NW 515. Additionally,there would be a potential interface between NG NW 515 and fixed NW 520.Main features of this architectural proposal include: (1) no changes tothe 4G RAN; and (2) such an architecture would include a new RAT design(e.g., NG NW 515) which could be optimized to fully benefit from newtechnologies such as virtualization. However, such an architecture couldonly be utilized where there is new RAT coverage, and there may bepotential signaling burdens due to mobility if the new RAT does notprovide seamless coverage.

FIG. 5C illustrates yet another implementation based on the principlesdescribed above. As shown, such an implementation would introduce NG NW515 which would include next generation network functions. Thus, therewould be defined interfaces between EPC 510 and 4G RAT 530, NG NW 515and next generation RAT 540, fixed NW 520 and fixed networks/Wi-Finetworks 550. Additionally, there would be defined interfaces between NGNW 515 and 4G RAT 530 and NG NW 515 and fixed networks/Wi-Fi networks550. Further, there would be a potential interface between NG NW 515 andEPC 510 as well as NG NW 515 and fixed NW 520. Main features of thisarchitectural proposal include a new RAT design (e.g., NG NW 515) whichcould be optimized to fully benefit from new technologies such asvirtualization, a sound migration path from older RAT technologies, andseamless coverage during mobility. However, such an architecture maystress legacy RANs, such as due to concurrent operation of legacyfunctions and new next generation functions.

Other issues with the above implementations include service continuitybetween various RATs as the next generation architecture will likelysupport more RATs than current architectures. Additionally, thecoexistence of current networks with the next generation network maycreate mobility issues for both legacy and next generation users.Further, next generation architectures will support control and userplane splitting, a minimization of network nodes and a simplification ofnetwork functions which may also impact continuity between differentRATs. Therefore, improvements in continuity between legacy RATs (e.g.,4G and 3G RATs) and next generation RATs are desirable.

Next Generation Network Interface Architecture for IP ConnectionContinuity

FIGS. 6A and 6B illustrate next generation network interfacearchitectures according to some embodiments. FIG. 6A illustrates a nextgeneration gateway, such as GW 606, that may interface with entitieswithin a legacy network, such as 4G NW 602 and entities within a nextgeneration network, such as NG NW 604. Thus, a first interface may bedefined between GW 606 and mobility management entity (MME) 632, whichmay be included in 4G NW 602. In addition, a second interface may bedefined between GW 606 and server gateway and packet gateway (SGW/PGW)622, which may also be included in 4G NW 602. Further, a third interfacemay be defined between GW 606 and next generation base station (eNB)614, which may be included in NG NW 604. Note that within 4G NW 602, alegacy base station such as eNB 612 may interface with both MME 632 andSGW/PGW 622. Further, there may be an interface between MME 632 andSGW/PGW 622. In addition, UE 106 may communicate wirelessly with botheNB 612 and eNB 614.

FIG. 6B illustrates another next generation architecture according toembodiments. As shown, GW 606 may interface with entities within legacynetwork 4G NW 602 and entities within next generation network NG NW 604.Thus, a first interface may be defined between GW 606 and mobilitymanagement entity (MME) 632, which may be included in 4G NW 602. Inaddition, a second interface may be defined between GW 606 and SGW1/PGW1622A and SGW2/PGW2 622B, which may both be included in 4G NW 602.Further, a third interface may be defined between GW 606 and eNB 614,which may be included in NG NW 604. Note that within 4G NW 602, a legacybase station such as eNB 612 may interface with both MME 632 andSGW1/PGW1 622A and SGW2/PGW2 622B. Further, there may be interfacesbetween MME 632 and SGW1/PGW1 622A and SGW2/PGW2 622B. In addition, UE106 may communicate wirelessly with both eNB 612 and eNB 614.

MME 632 may be or include any switch, server, or other node within 4G NW602. Thus, MME 632 may include a portion of, or all of, the elementsdescribed above in reference to base station 102. Hence, MME 632 mayinclude one or more processing elements (or processors) which mayexecute program instructions and the processing elements may be coupledto a memory management unit, which may be configured to receiveaddresses from the processing elements and translate those addresses tolocations in a memory or to other circuits or devices. In addition, MME632 may include at least one network port and one or more antennascoupled to at least one radio. MME 632 may be configured to operate as awireless transceiver and may be further configured to communicate withUE devices, such as UE 106 using various wireless communicationstandards.

In addition, eNB 612 may be a legacy base station and may be configuredas described above with reference to FIG. 4 and base station 102. Thus,eNB 612 may be configured to communicate using various legacy wirelesscommunication standards such as LTE, LTE-A, GSM, UMTS, CDMA2000, Wi-Fi,etc.

Further, eNB 614 may be a next generation base station and may includecomponents similar to the components described above with reference tobase station 102. Thus, eNB 614 may include one or more processingelements (or processors) which may execute program instructions. Theprocessing elements may be coupled to a memory management unit, whichmay be configured to receive addresses from the processing elements andtranslate those addresses to locations in a memory or to other circuitsor devices. In addition, eNB 614 may include at least one network portand one or more antennas coupled to at least one radio. Further, eNB 614may be configured to operate as a wireless transceiver and may befurther configured to communicate with UE devices, such as UE 106 usinga next generation wireless communication standards, such as a NG RAT.

In some embodiments, if UE 106 first attaches from NG NW 604 and alsoselects GW 606 as further described below, SGW1/PGW1 622A may also beassigned to UE 106. Thus, when UE 106 moves back to 4G NW 602, MME 632may select SGW1/PGW1 since it has already been assigned. In addition, insome embodiments, if UE 106 first attaches from 4G NW 602, MME 632 mayselect a default SGW/PGW such as SGW2/PGW2 622B based on a DNS query. Asfurther described below, SGW2/PGW2 622B may be mapped to GW 606. Thus,when UE 106 moves to NG NW 604, GW 606 may be selected by eNB 614 basedon the mapping. In addition, when UE 106 returns to 4G NW 602, MME 632will again select SGW2/PGW2 622B instead of performing the DNS query.Thus, whether UE 106 first attaches from 4G NW 602 or NG NW 604, IPconnection continuity (e.g., original IP address and first SGW/PGW andGW) will be maintained as UE 106 moves between networks.

Turning now to FIGS. 7A-7B and 8, communications between the variousentities illustrated in FIG. 6 will be described. The communications mayallow IP connection continuity while switching between 4G NW 602 and NGNW 604.

FIG. 7A illustrates a signaling diagram for maintaining IP continuitybetween legacy and next generation RATs, according to some embodiments.The signaling shown in FIG. 7A may be used in conjunction with any ofthe systems or devices shown in the above Figures, among other devices.In various embodiments, some of the signals shown may be performedconcurrently, in a different order than shown, or may be omitted.Additional signaling may also be performed as desired.

At 702, UE 106 may send a message to a legacy base station, such as eNB612. The message may include a request to attach to eNB 612. In someembodiments, the message may be a radio resource control (RRC)connection request. In some embodiments, the message may include anattach request and a packet data network (PDN) connectivity request.

At 704, eNB 612 may send a message to MME 632. The message may includethe request from UE 106 to attach to eNB 612. In some embodiments, themessage may include the attach request and/or the PDN connectivityrequest. In some embodiments, the message may be an S1 message.

At 706, UE 106 may send an additional message to MME 632. In someembodiments, the message may be an attach message (e.g., a non-accessstratum (NAS) message).

At 708, MME 632 may send a message to home subscriber server (HSS) 616to authenticate UE 106. In some embodiments, the message may includevarious parameters such as visited public land mobile networkidentification (PLMN ID) as well as subscription information. In someembodiments, the message may be or include an authentication informationrequest.

At 710, HSS 616 may send a message to MME 632. In some embodiments, themessage may include authentication information for authenticating UE106. In addition, the message may include subscription information. MME632 may determine, based at least in part on the message received fromHSS 616 whether UE 106 supports a next generation RAT. For example, MME632 may determine whether UE 106 subscribes to (or whether UE 106 isassociated with a subscription for) the next generation RAT.

At 712, MME 632, in response to determining that UE 106 supports (and/orsubscribes to) a next generation RAT, may send a message to gateway 606via the first interface (between the gateway 606 and the MME 632)described above in reference to FIG. 6. In some embodiments, the messagemay include a request to create a session. In other words, the messagemay be a create session request message. In such embodiments, MME 632may select GW 606 based at least in part on a domain name system (DNS)server retrieval. In addition, a default SGW/PGW may be arranged tocorrespond to GW 606.

At 714, GW 606 may send a message to MME 632 via the first interface(between the gateway 606 and the MME 632) described above in referenceto FIG. 6. In some embodiments, the message may include sessioninformation such as an IP address. IN some embodiments, the message bybe a create session response.

At 716, MME 632 may send a message to UE 106 indicating that attachmentto GW 606 was successful. In some embodiments, the message may includethe IP address from GW 606. In some embodiments, MME 632 may send themessage to eNB 612 and eNB 612 may forward the message to UE 106.

FIG. 7B illustrates a signaling diagram for maintaining IP continuitybetween legacy and next generation RATs, according to some embodiments.The signaling shown in FIG. 7B may be used in conjunction with any ofthe systems or devices shown in the above Figures, among other devices.In various embodiments, some of the signals shown may be performedconcurrently, in a different order than shown, or may be omitted.Additional signaling may also be performed as desired.

At 722, UE 106 may send a message to a next generation base station,such as eNB 614. The message may include a request to attach to eNB 614.In some embodiments, the message may be a radio resource control (RRC)connection request. In some embodiments, the message may include anattach request and a packet data network (PDN) connectivity request.

At 724, eNB 614 may send a message to home subscriber server (HSS) 616to authenticate UE 106. In some embodiments, the message may includevarious parameters such as visited public land mobile networkidentification (PLMN ID) as well as subscription information. In someembodiments, the message may be or include an authentication informationrequest.

At 726, HSS 616 may send a message to eNB 614. In some embodiments, themessage may include authentication information for authenticating UE106. In addition, the message may include subscription information. eNB614 may determine, based at least in part on the message received fromHSS 616 whether UE 106 supports a next generation RAT. For example, eNB614 may determine whether UE 106 subscribes to (or whether UE 106 isassociated with a subscription for) the next generation RAT.

At 728, eNB 614, in response to determining that UE 106 supports (and/orsubscribes to) a next generation RAT, may send a message to gateway 606via the third interface (between the gateway 606 and the eNB 614)described above with reference to FIG. 6. In some embodiments, themessage may include a request to create a session. In other words, themessage may be a create session request message. In such embodiments,eNB 614 may select GW 606 based at least in part on a domain name system(DNS) server retrieval. In addition, a default SGW/PGW may be arrangedto correspond to GW 606.

Note that in some embodiments, if eNB 614 determines that UE 106 doesnot support the next generation RAT, eNB 614 may reject UE 106'sattachment request and request UE 106 re-attach from a legacy RAT asdescribed above with reference to FIG. 7A.

At 730, GW 606 may send a message to eNB 614 via the third interface(between the gateway 606 and the eNB 614) described above with referenceto FIG. 6. In some embodiments, the message may include sessioninformation such as an IP address. In some embodiments, the message bybe a create session response.

At 732, eNB 614 may send a message to UE 106 indicating that attachmentto GW 606 was successful. In some embodiments, the message may includethe IP address from GW 606.

FIG. 8 illustrates a signaling diagram for maintaining IP continuitybetween legacy and next generation RATs, according to some embodiments.The signaling shown in FIG. 8 may be used in conjunction with any of thesystems or devices shown in the above Figures, among other devices. Invarious embodiments, some of the signals shown may be performedconcurrently, in a different order than shown, or may be omitted.Additional signaling may also be performed as desired.

At 802, UE 106 may send a message to a legacy base station, such as eNB612. The message may include a request to attach to eNB 612. In someembodiments, the message may be a radio resource control (RRC)connection request. In some embodiments, the message may include anattach request and a packet data network (PDN) connectivity request.

At 804, eNB 612 may send a message to MME 632. The message may includethe request from UE 106 to attach to eNB 612. In some embodiments, themessage may include the attach request and/or the PDN connectivityrequest. In some embodiments, the message may be an S1 message.

At 806, UE 106 may send an additional message to MME 632. In someembodiments, the message may be an attach message (e.g., a non-accessstratum (NAS) message).

At 808, MME 632 may send a message to home subscriber server (HSS) 616to authenticate UE 106. In some embodiments, the message may includevarious parameters such as visited public land mobile networkidentification (PLMN ID) as well as subscription information. In someembodiments, the message may be or include an authentication informationrequest.

At 810, HSS 616 may send a message to MME 632. In some embodiments, themessage may include authentication information for authenticating UE106. In addition, the message may include subscription information. MME632 may determine, based at least in part on the message received fromHSS 616 whether UE 106 supports a next generation RAT. For example, MME632 may determine whether UE 106 subscribes to (or whether UE 106 isassociated with a subscription for) the next generation RAT.

At 812, MME 632, in response to determining that UE 106 supports (and/orsubscribes to) a next generation RAT, may send a message to UE 106indicating that attachment has been rejected. In some embodiments, themessage may trigger UE 106 to attempt attachment to GW 606 via eNB 614.

At 814, UE 106 may send a message to a next generation base station,such as eNB 614 in response to receiving the message from MME 632indicating attachment had been rejected. The message may include arequest to attach to eNB 614. In some embodiments, the message may be aradio resource control (RRC) connection request. In some embodiments,the message may include an attach request and a packet data network(PDN) connectivity request.

At 816, eNB 614 may send a message to home subscriber server (HSS) 616to authenticate UE 106. In some embodiments, the message may includevarious parameters such as visited public land mobile networkidentification (PLMN ID) as well as subscription information. In someembodiments, the message may be or include an authentication informationrequest.

At 818, HSS 616 may send a message to eNB 614. In some embodiments, themessage may include authentication information for authenticating UE106. In addition, the message may include subscription information. eNB614 may determine, based at least in part on the message received fromHSS 616 whether UE 106 supports a next generation RAT. For example, eNB614 may determine whether UE 106 subscribes to (or whether UE 106 isassociated with a subscription for) the next generation RAT.

At 820, eNB 614, in response to determining that UE 106 supports (and/orsubscribes to) a next generation RAT, may send a message to gateway 606via the third interface (between the gateway 606 and the eNB 614)described above with reference to FIG. 6. In some embodiments, themessage may include a request to create a session. In other words, themessage may be a create session request message. In such embodiments,eNB 614 may select GW 606 based at least in part on a domain name system(DNS) server retrieval. In addition, a default SGW/PGW may be arrangedto correspond to GW 606.

At 822, GW 606 may send a message to eNB 614 via the third interface(between the gateway 606 and the eNB 614) described above with referenceto FIG. 6. In some embodiments, the message may include sessioninformation such as an IP address. In some embodiments, the message bybe a create session response.

At 824, eNB 614 may send a message to UE 106 indicating that attachmentto GW 606 was successful. In some embodiments, the message may includethe IP address from GW 606.

FIGS. 9A-9B DNS Retrieval Procedure

FIGS. 9A and 9B illustrate signaling diagrams for a DNS query accordingto some embodiments. In particular, FIG. 9A illustrates a signalingdiagram between a mobility management entity (e.g., MME 632) of a legacyRAT and a domain name system (DNS) server, and FIG. 9B illustrates asignaling diagram between a base station (e.g., eNB 614) in a nextgeneration RAT and the DNS server. Note that the signaling shown inFIGS. 9A and 9B may be used in conjunction with any of the systems ordevices shown in the above Figures, among other devices. In variousembodiments, some of the signals shown may occur concurrently, in adifferent order than shown, or may be omitted. Additional signaling mayalso be performed as desired.

Turning to FIG. 9A, at 902, MME 632 may send a first query to DNS 922.The first query may include a request for a PGW for a legacy mobilenetwork. In other words, the first query may include a request for anaccess point name (APN) for the legacy mobile network (e.g., 3G or 4G).

At 904, DNS 922 may send a first response to MME 632. The first responsemay include a PGW address list. The address list may include availablePGWs for the legacy mobile network.

At 906, MME 632 may send a second query to DNS 922. The second query mayinclude a request for a PGW for a next generation mobile network. Inother words, the second query may include a request for an APN for thenext generation mobile network.

Note that in some embodiments, MME 632 may only send one query to DNS922 and may receive an access point name for the PGW for the nextgeneration mobile network. In addition, in some embodiments, if MME 632receives the access point name for the PGW for the next generationmobile network, MME 632 may send a query to DNS 922 and may receive alist of SGW/PGW and PGW addresses for the next generation mobile networkand, based on the list, MME 632 may select an SGW/PGW and GW for UE 106.

In some embodiments, DNS 922 may have a mapping relationship betweenPGWs for legacy mobile networks (legacy PGWs) and PGWs for the nextgeneration mobile network (NG PGWs). Such a mapping between legacy PGWsand NG PGWs may allow for (or enable) IP address continuity as a UEmoves from legacy RATs and the next generation RAT and back.

In some embodiments, for the mapping relation between legacy PGWs(and/or SGWs) and GW for next generation SGW/PGW (legacy) and NG PGWsmay be associated with a particular UE, such as UE 106. In suchembodiments, DNS 922 may record a mapping table of SGW/PGW addresses andGWs addresses. In some embodiments, the mapping table may have aplurality of legacy SGW/PGWs and a plurality of NG GWs associated withthe particular UE. In some embodiments, DNS 922 may ensure that for theparticular UE in a certain period, the same legacy SGW/PGW and NG GWwill be assigned to the particular UE. In other words, for a givenperiod of time and/or location of the particular UE, the same legacySGW/PGW and NG GW will be selected to ensure IP address continuity asthe UE moves between legacy and next generation networks.

At 908, DNS 922 may send a second response to MME 632. The secondresponse may include a NG PGW address list. In some embodiments, thesecond response may also include the mapping between legacy PGWs and NGPGWs.

Turning to FIG. 9B, at 910, eNB 614 may send a first query to DNS 922.The first query may include a request for a PGW for a next generationmobile network. In other words, the second query may include a requestfor an APN for the next generation mobile network.

In some embodiments, DNS 922 may have a mapping relationship betweenPGWs for legacy mobile networks (legacy PGWs) and PGWs for the nextgeneration mobile network (NG PGWs). Such a mapping between legacy PGWsand NG PGWs may allow for (or enable) IP address continuity as a UEmoves from legacy RATs and the next generation RAT and back.

At 912, DNS 922 may send a first response to eNB 614. The first responsemay include a NG PGW address list. In some embodiments, the secondresponse may also include the mapping between legacy PGWs and NG PGWs.

Next Generation Protocol Stack

FIG. 10 illustrates a protocol stack for a next generation wirelesscommunication system according to some embodiments. Note that theprotocol stack illustrated is only one of many possible protocol stacksthat may be implemented in a next generation wireless communicationsystem. Note further, additional features, elements, and/or layers maybe added to protocol stack shown.

As shown, the protocol stack may include existing interfaces such asLTE-Uu between UE 106 and eNB 612, an S1-U (e.g., reference pointbetween E-UTRAN and SGW for per bearer user plane tunneling and intereNB path switching during handover) interface between eNB 612 and SGW622A, an S5/S8 (e.g., S5 may be for providing user plane tunneling andtunnel management between SGW and PGW, may be used for SGW relocationdue to UE mobility and for SGW connecting to a non-collocated PGW forPDN connectivity and S8 may be an inter-PLMN variant of S5 interface)interface between SGW 622A and PDN GW 622B, and an SGi (e.g., referencepoint between PGW and the PDN) interface. At UE 106, the protocol stackmay include layers L1, MAC, RLC, PDCP, and IP as well as new layer IP′for addressing within the next generation RAN. Thus, UE 106 may maintainIP addresses associated with legacy RANs and the next generation RAN.Further, this may allow for IP address continuity as UE 106 movesbetween RANs. Protocol stacks for eNB 612 may include layers L1, L2,UDP/IP, and PDCP to communicate with UE 106 and layers L1, L2, UDP/IP,and GTP-U to communicate with SGW 622A. Protocol stacks for SGW 622A mayinclude layers L1, L2, UDP/IP, and GTP-U to communicate with eNB 612 andlayers L1, L2, UDP/IP, and GTP-U to communicate with PDN GW 622B. Aprotocol stack for PDN GW 622B may include layers L1, L2, UDP/IP, andGTP-U for communication with SGW 622A and an IP layer for communicationwith UE 106. In addition, a protocol stack for GW 606 may include layersL1, L2, UDP/IP, and GTP-U, and IP as well as an IP′ layer forcommunication with UE 106. Note that in some embodiments, the protocolstack may not include the IP′ layer and GW 606 may communicate with UE106 via the IP layer.

Attachment Method

FIG. 11A illustrates an example of a method for a wireless device, suchas UE 106, to attach to a next generation gateway, such as GW 606,according to some embodiments. The method shown in FIG. 11A may be usedin conjunction with any of the systems or devices shown in the aboveFigures, among other devices. In various embodiments, some of the methodelements shown may be performed concurrently, in a different order thanshown, or may be omitted. Additional method elements may also beperformed as desired. As shown, this method may operate as follows.

At 1102, an attachment request for a wireless device may be received. Insome embodiments, the attachment request may be received from thewireless device. In other embodiments, the attachment request may bereceived from a base station of a legacy radio access network (RAN). Inother words, the base station may be configured to communicate via oneor more legacy RATs such as LTE, LTE-A, GSM, UMTS, CDMA2000, Wi-Fi, etc.In some embodiments, the request may include a packet data network (PDN)connectivity request.

At 1104, authentication of the wireless device may be determined viacommunication with a home subscriber server (HSS). In some embodiments,determining authentication via communication with the HSS may includesending an authentication request to the HSS and receiving theauthentication information from the HSS.

At 1106, capabilities of the wireless device may be determined. In someembodiments, determining capabilities of the wireless device may includedetermining, based at least in part on the authentication information,whether the wireless device is capable of communication via the nextgeneration RAN. In some embodiments, the authentication information mayinclude subscription information associated with the wireless device. Inother words, determining the capabilities of the wireless device mayinclude determining whether there is a subscription to the nextgeneration RAN associated with the wireless device.

At 1108, a connection request may be sent to a gateway of the nextgeneration RAN. In some embodiments, the connection request may be sentin response to determining the capabilities of the wireless device.Alternatively, in some embodiments, where the attachment request isreceived from a base station (e.g., received by an MME of a legacy RAN),a message may be sent to the wireless device in response to determiningthat the wireless device is capable of communication via the nextgeneration RAN. The message may indicate that the connection request hasbeen denied and may further include a request for the wireless device toattach via the next generation RAN (e.g., the wireless device may attachvia a base station of the next generation RAN).

In some embodiments, a session response may be received from the gatewayand may indicate that the session request has been accepted.Additionally, a message indicating that the attachment request has beenaccepted may be sent to the wireless device. In some embodiments, thesession response may include an IP address of the gateway. Additionally,in some embodiments, the message may include the IP address.

In some embodiments, where the attachment request is received from thewireless device (e.g., received by a base station of the next generationRAN), a message may be sent to the wireless device in response todetermining that the wireless device is not capable of communication viathe next generation RAN. The message may indicate that the connectionrequest has been denied and may further include a request for thewireless device to attach via a legacy RAN. In some embodiments,determining that the wireless device is not capable of communication viathe next generation RAN may include determining that the wireless deviceis not associated with a subscription to the next generation RAN.

In some embodiments, where the attachment request is received from thewireless device (e.g., received by a base station of the next generationRAN), a query may be sent to a domain name system (DNS) server and thequery may include a request for an internet protocol (IP) address for agateway of the next generation RAN. In addition, a response may bereceived from the DNS server and may include a list of IP addresses forgateways of the next generation RAN. In some embodiments, the responsemay also include a mapping between the IP addresses for gateways of thenext generation RAN and IP addresses for gateways of legacy RANs.

In some embodiments, where the attachment request is received from abase station (e.g., received by an MME of a legacy RAN), a first querymay be sent to a domain name system (DNS) server and the first query mayinclude a request for an internet protocol (IP) address for a gateway ofthe legacy RAN. In addition, a first response may be received from theDNS server and may include a list of IP addresses for gateways of thelegacy RAN. Further, a second query a query may be sent to the DNSserver and the second query may include a request for an internetprotocol (IP) address for a gateway of the next generation RAN.Additionally, a second response may be received from the DNS server andmay include a list of IP addresses for gateways of the next generationRAN. In some embodiments, the second response may also include a mappingbetween the IP addresses for gateways of the next generation RAN and IPaddresses for gateways of legacy RANs.

FIG. 11B illustrates a processing element including modules forattaching a wireless device, such as UE 106, to a next generationgateway, such as GW 606, according to some embodiments. In someembodiments, antenna 1135 may be coupled to processing element 1164. Theprocessing element may be configured to perform the method describedabove in reference to FIG. 11A. In some embodiments, processing element764 may include one or more modules, such as modules (or circuitry)1122-1128, and the modules (or circuitry) may be configured to performvarious steps of the method described above in reference to FIG. 11A. Insome embodiments, the processing element may be included in a mobilitymanagement entity, such as MME 632. In other embodiments, the processingelement may be included in a base station, such as eNB 614. As shown,the modules may be configured as follows.

In some embodiments, processing element 1164 may include a receivemodule 1122 configured to receive an attachment request for a wirelessdevice. In some embodiments, the attachment request may be received fromthe wireless device. In other embodiments, the attachment request may bereceived from a base station of a legacy radio access network (RAN). Inother words, the base station may be configured to communicate via oneor more legacy RATs such as LTE, LTE-A, GSM, UMTS, CDMA2000, Wi-Fi, etc.In some embodiments, the request may include a packet data network (PDN)connectivity request.

In some embodiments, processing element 1164 may include a firstdetermine module 1124 configured to determine authentication of thewireless device via communication with a home subscriber server (HSS).In some embodiments, determining authentication via communication withthe HSS may include sending an authentication request to the HSS andreceiving the authentication information from the HSS.

In some embodiments, processing element 1164 may include a seconddetermine module 1126 configured to determine capabilities of thewireless device. In some embodiments, determining capabilities of thewireless device may include determining, based at least in part on theauthentication information, whether the wireless device is capable ofcommunication via the next generation RAN. In some embodiments, theauthentication information may include subscription informationassociated with the wireless device. In other words, determining thecapabilities of the wireless device may include determining whetherthere is a subscription to the next generation RAN associated with thewireless device.

In some embodiments, processing element 1164 may include a send module1128 configured to send a connection request to a gateway of the nextgeneration RAN. In some embodiments, the connection request may be sentin response to determining the capabilities of the wireless device.Alternatively, in some embodiments, where the attachment request isreceived from a base station (e.g., received by an MME of a legacy RAN),the send module may be configured to send a message to the wirelessdevice in response to determining that the wireless device is capable ofcommunication via the next generation RAN. The message may indicate thatthe connection request has been denied and may further include a requestfor the wireless device to attach via the next generation RAN (e.g., thewireless device may attach via a base station of the next generationRAN).

It is apparent for those skilled in the art that, for the particularprocesses of the modules (or circuitry) described above (such as modules1122, 1124, 1126, and 1128), reference may be made to the correspondingsteps (such as steps 1102, 1104, 1106, and 1108, respectively) in therelated process embodiment sharing the same concept and the reference isregarded as the disclosure of the related modules (or circuitry) aswell. Furthermore, processing element 1164 may be implemented insoftware, hardware or combination thereof. More specifically, processingelement 1164 may be implemented as circuits such as an ASIC (ApplicationSpecific Integrated Circuit), portions or circuits of individualprocessor cores, entire processor cores, individual processors,programmable hardware devices such as a field programmable gate array(FPGA), and/or larger portions of systems that include multipleprocessors. Additionally, processing element 1164 may be implemented asa general-purpose processor such as a CPU, and therefore each module canbe implemented with the CPU executing instructions stored in a memorywhich perform a respective step.

Embodiments of the present disclosure may be realized in any of variousforms. For example some embodiments may be realized as acomputer-implemented method, a computer-readable memory medium, or acomputer system. Other embodiments may be realized using one or morecustom-designed hardware devices such as ASICs. Still other embodimentsmay be realized using one or more programmable hardware elements such asFPGAs.

In some embodiments, a non-transitory computer-readable memory mediummay be configured so that it stores program instructions and/or data,where the program instructions, if executed by a computer system, causethe computer system to perform a method, e.g., any of a methodembodiments described herein, or, any combination of the methodembodiments described herein, or, any subset of any of the methodembodiments described herein, or, any combination of such subsets.

In some embodiments, a device (e.g., a UE 106) may be configured toinclude a processor (or a set of processors) and a memory medium, wherethe memory medium stores program instructions, where the processor isconfigured to read and execute the program instructions from the memorymedium, where the program instructions are executable to implement anyof the various method embodiments described herein (or, any combinationof the method embodiments described herein, or, any subset of any of themethod embodiments described herein, or, any combination of suchsubsets). The device may be realized in any of various forms.

Although the embodiments above have been described in considerabledetail, numerous variations and modifications will become apparent tothose skilled in the art once the above disclosure is fully appreciated.It is intended that the following claims be interpreted to embrace allsuch variations and modifications.

What is claimed is:
 1. A mobility management entity (MME) within fourthgeneration (4G) network, comprising: a memory; and a processing elementin communication with the memory, wherein the processing element isconfigured to: receive, from a base station of the 4G network operatingaccording to a 4G legacy radio access technology (RAT) within the 4Gnetwork, an attachment request for a wireless device; determine thewireless device is associated with a subscription for a fifth generation(5G) RAT within a 5G network; select, based at least in part ondetermining that the wireless device is associated with the subscriptionfor the 5G network, a first gateway that interfaces the 4G network andthe 5G network, wherein the first gateway has a first user planeinterface to a first base station of the 5G network and a second userplane interface with the base station of the 4G network through one ormore 4G network gateways, wherein the first user plane interface fromthe first gateway to the first base station of the 5G network does notinclude any intervening 5G network gateway, and wherein the selection ofthe first gateway enables internet protocol (IP) address continuity withthe first gateway in subsequent connections through a second basestation of the 5G network operating according to the 5G RAT; send, tothe first gateway, a request to create a session to create a connectionfor the wireless device with the first gateway; receive a create sessionresponse including session information for connecting to the 5G network;and send, to the wireless device, a message indicating that attachmentto the first gateway was successful.
 2. The MME of claim 1, wherein theprocessing element is further configured to: send an authenticationrequest to a home subscriber server (HSS), wherein the authenticationrequest includes first subscription information associated with thewireless device; and receive authentication information forauthenticating the wireless device from the HSS, wherein theauthentication information comprises second subscription informationassociated with the wireless device.
 3. The MME of claim 1, wherein theprocessing element is further configured to: send a query to a domainname system (DNS) server, wherein the query includes a request for aninternet protocol (IP) address for a gateway of the 4G network; andreceive a response from the DNS server, wherein the response includes alist of IP addresses for gateways of the 4G network.
 4. The MME of claim3, wherein the query includes a request for an access point name (APN)for the 4G network.
 5. The MME of claim 1, wherein the processingelement is further configured to: send a query to a domain name system(DNS) server, wherein the query includes a request for an IP address fora gateway of the 5G network; and receive a response from the DNS server,wherein the response includes a list of IP address for gateways of the5G network.
 6. The MME of claim 5, wherein the query includes a requestfor an access point name (APN) for the 5G network.
 7. The MME of claim1, wherein a response to a query from a domain name system (DNS) serverincludes a mapping of the IP addresses for one or more gateways betweenthe 5G network and the 4G network.
 8. The MME of claim 1, wherein thesession information comprises the IP address.
 9. The MME of claim 1,wherein the attachment request includes a packet data network (PDN)connectivity request.
 10. A non-transitory computer accessible memorymedium comprising program instructions which, when executed by amobility management entity (MME), cause the MME to: receive, from a basestation of a 4G network operating according to a 4G legacy radio accesstechnology (RAT) within the 4G network, an attachment request for awireless device; determine the wireless device is associated with asubscription for a fifth generation (5G) RAT within a 5G network;select, based at least in part on determining that the wireless deviceis associated with the subscription for the 5G network, a first gatewaythat interfaces the 4G network and the 5G network, wherein the firstgateway has a first user plane interface to a first base station of the5G network and a second user plane interface with the base station ofthe 4G network through one or more 4G network gateways, wherein thefirst user plane interface from the first gateway to the first basestation of the 5G network does not include any intervening 5G networkgateway, and wherein the selection of the first gateway enables internetprotocol (IP) address continuity with the first gateway in subsequentconnections through a second base station of the 5G network operatingaccording to the 5G RAT; send, to the first gateway, a request to createa session to create a connection for the wireless device with the firstgateway; receive a create session response including session informationfor connecting to the 5G network; and send, to the wireless device, amessage indicating that attachment to the first gateway was successful.11. The non-transitory computer accessible memory medium of claim 10,wherein the program instructions are further executable to cause the MMEto: send an authentication request to a home subscriber server (HSS),wherein the authentication request includes first subscriptioninformation associated with the wireless device; and receiveauthentication information for authenticating the wireless device fromthe HSS, wherein the authentication information comprises secondsubscription information associated with the wireless device.
 12. Thenon-transitory computer accessible memory medium of claim 10, whereinthe program instructions are further executable to cause the MME to:send a query to a domain name system (DNS) server, wherein the queryincludes a request for an internet protocol (IP) address for a gatewayof the 4G network; and receive a response from the DNS server, whereinthe response includes a list of IP addresses for gateways of the 4Gnetwork; and wherein the query includes a request for an access pointname (APN) for the 4G network.
 13. The non-transitory computeraccessible memory medium of claim 10, wherein the program instructionsare further executable to cause the MME to: send a query to a domainname system (DNS) server, wherein the query includes a request for an IPaddress for a gateway of the 5G network; and receive a response from theDNS server, wherein the response includes a list of IP address forgateways of the 5G network; and wherein the query includes a request foran access point name (APN) for the 5G network.
 14. The non-transitorycomputer accessible memory medium of claim 10, wherein a response to aquery from a domain name system (DNS) server includes a mapping of theIP addresses for one or more gateways between the 5G network and the 4Gnetwork.
 15. The non-transitory computer accessible memory medium ofclaim 10, wherein the session information comprises the IP address. 16.The non-transitory computer accessible memory medium of claim 10,wherein the attachment request includes a packet data network (PDN)connectivity request.
 17. An apparatus, comprising: a memory; and atleast one processor in communication with the memory, wherein the atleast one processor is configured to: receive, from a base station of a4G network operating according to a 4G legacy radio access technology(RAT) within the 4G network, an attachment request for a wirelessdevice; determine the wireless device is associated with a subscriptionfor a fifth generation (5G) RAT within a 5G network; select, based atleast in part on determining that the wireless device is associated withthe subscription for the 5G network, a first gateway that interfaces the4G network and the 5G network, wherein the first gateway has a firstuser plane interface to a first base station of the 5G network and asecond user plane interface with the base station of the 4G networkthrough one or more 4G network gateways, wherein the first user planeinterface from the first gateway to the first base station of the 5Gnetwork does not include any intervening 5G network gateway, and whereinthe selection of the first gateway enables internet protocol (IP)address continuity with the first gateway in subsequent connectionsthrough a second base station of the 5G network operating according tothe 5G RAT; generate instructions to send, to the first gateway, arequest to create a session to create a connection for the wirelessdevice with the first gateway; receive a create session responseincluding session information for connecting to the 5G network; andgenerate instructions to send, to the wireless device, a messageindicating that attachment to the first gateway was successful.
 18. Theapparatus of claim 17, wherein the at least one processor is furtherconfigured to: generate instructions to send an authentication requestto a home subscriber server (HSS), wherein the authentication requestincludes first subscription information associated with the wirelessdevice; and receive authentication information for authenticating thewireless device from the HSS, wherein the authentication informationcomprises second subscription information associated with the wirelessdevice.
 19. The apparatus of claim 17, wherein the session informationcomprises the IP address.
 20. The apparatus of claim 17, wherein theattachment request includes a packet data network (PDN) connectivityrequest.